Skip to content

Implement multi-use snapshots - #3615

Merged
tseaver merged 19 commits into
masterfrom
spanner-multi_use_snapshot
Jul 26, 2017
Merged

tseaver merged 19 commits into
masterfrom
spanner-multi_use_snapshot

Conversation

@tseaver

@tseaver tseaver commented Jul 17, 2017

Copy link
Copy Markdown
Contributor

Multi-use snapshots trigger an "implicit" server-side transaction, and capture its ID on the first request. Subsequent requests return that ID, allowing for isolation from other changes. We default to multi_use=False because that mode is much more performant for the simple case.

This feature is one which we originally decided to leave out, but the P0 system test list requires that it be implemented.

I think that a commitwise review might be easier than reviewing the whole enchilada.

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: spanner Issues related to the Spanner API. cla: yes This human has signed the Contributor License Agreement. priority: p0 Highest priority. Critical issue. P0 implies highest priority. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants